 |
|
|
 |
| Subject: NSD reading |
 |
 |
 |
| Product Area: Domino Server |
 |
| Technical Area: Specification |
 |
| Platform: Not Applicable |
 |
| Release: 8.5.1 |
 |
| Reproducible: Not applicable |
 |
 |
 |
 |
Hi,
I'd like to know what FP, PC and SP mean in thread header that NSD output?
############################################################
### FATAL THREAD 57/96 [ Task: 18a0: 01e4]
### FP=0x00000000, PC=0x0042bf2e, SP=0x2b56da4c
### stkbase=2b570000, total stksize=32768, used stksize=9652
### EAX=0x2d9cfc40, EBX=0x00000000, ECX=0x00000001, EDX=0x00000000
### ESI=0x2b56f650, EDI=0x2b56ddc8, CS=0x0000001b, SS=0x00000023
### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010202
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
My understanding that everything from EAX= to Flags= is the CPU registry information.
I also assume that FP is a Frame poiner (saved in EBP), PC - (don't know how to transtate the acronym, "procedure call" may be) points out to the code segment where the current function is located (saved in EIP), SP - Stack Pointer (saved in ESP).
Why doesn't NSD use EBP, EIP and ESP registry names instead of FP, SP and PC?
Thank you
Sergey
 
Feedback number WEBB7YJVK6 created by ~Lisa Bretumiplopings on 12/08/2009
Status: Open
Comments:
|
| |
|
Return to top
Printer-friendly
